🛠️ All DevTools

[Other] Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: &#x2F;plugin marketplace add jshchnz&#x2F;claude-code-scheduler &#x2F;plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.

[CLI Tool] Show HN: A fast CLI and MCP server for managing Lambda cloud GPU instances I built an unofficial CLI and MCP server for Lambda cloud GPU instances.<p>The main idea: your AI agents can now spin up and manage Lambda GPUs for you.<p>The MCP server exposes tools to find, launch, and terminate instances. Add it to Claude Code, Cursor, or any agent with one command and you can say things like &quot;launch an H100, ssh in, and run big_job.py&quot;<p><pre><code> Other features: - Notifications via Slack, Discord, or Telegram when instances are SSH-ready - 1Password support for API keys - Also includes a standalone CLI with the same functionality </code></pre> Written in Rust. MIT licensed.<p>Note: This is an unofficial community project, not affiliated with Lambda.

[Other] Upgrading DrizzleORM logging with AsyncLocalStorage

[Other] Luxury Yacht is a desktop app for managing Kubernetes clusters

[CLI Tool] Show HN: Grsh – A high-performance shell for FreeBSD written in Rust I built GRSH because I wanted a modern, memory-safe shell that feels native to FreeBSD but works seamlessly on macOS.<p>While there are many shells out there, GRSH is my take on a minimal, fast, and secure command interpreter written entirely in Rust. It&#x27;s designed for users who want the safety guarantees of Rust without the overhead of more bloated alternatives.<p>I&#x27;m currently working on the official FreeBSD port. I’d love to get feedback on the shell&#x27;s behavior and performance from the community.<p>Github: <a href="https:&#x2F;&#x2F;github.com&#x2F;antoniomalara301289&#x2F;grsh" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;antoniomalara301289&#x2F;grsh</a>

[Other] Show HN: wxpath – Declarative web crawling in XPath <i>wxpath</i> is a declarative web crawler where web crawling and scraping are expressed directly in XPath.<p>Instead of writing imperative crawl loops, you describe what to follow and what to extract in a single expression:<p><pre><code> import wxpath # Crawl, extract fields, build a Wikipedia knowledge graph path_expr = &quot;&quot;&quot; url(&#x27;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Expression_language&#x27;) &#x2F;&#x2F;&#x2F;url(&#x2F;&#x2F;main&#x2F;&#x2F;a&#x2F;@href[starts-with(., &#x27;&#x2F;wiki&#x2F;&#x27;) and not(contains(., &#x27;:&#x27;))]) &#x2F;map{ &#x27;title&#x27;: (&#x2F;&#x2F;span[contains(@class, &quot;mw-page-title-main&quot;)]&#x2F;text())[1] ! string(.), &#x27;url&#x27;: string(base-uri(.)), &#x27;short_description&#x27;: &#x2F;&#x2F;div[contains(@class, &#x27;shortdescription&#x27;)]&#x2F;text() ! string(.), &#x27;forward_links&#x27;: &#x2F;&#x2F;div[@id=&quot;mw-content-text&quot;]&#x2F;&#x2F;a&#x2F;@href ! string(.) } &quot;&quot;&quot; for item in wxpath.wxpath_async_blocking_iter(path_expr, max_depth=1): print(item) </code></pre> The key addition is a `url(...)` operator that fetches and returns HTML for further XPath processing, and `&#x2F;&#x2F;&#x2F;url(...)` for deep (or paginated) traversal. Everything else is standard XPath 3.1 (maps&#x2F;arrays&#x2F;functions).<p>Features:<p>- Async&#x2F;concurrent crawling with streaming results<p>- Scrapy-inspired auto-throttle and polite crawling<p>- Hook system for custom processing<p>- CLI for quick experiments<p>Another example, paginating through HN comments (via &quot;follow=&quot; argument) pages and extracting data:<p><pre><code> url(&#x27;https:&#x2F;&#x2F;news.ycombinator.com&#x27;, follow=&#x2F;&#x2F;a[text()=&#x27;comments&#x27;]&#x2F;@href | &#x2F;&#x2F;a[@class=&#x27;morelink&#x27;]&#x2F;@href) &#x2F;&#x2F;tr[@class=&#x27;athing&#x27;] &#x2F;map { &#x27;text&#x27;: .&#x2F;&#x2F;div[@class=&#x27;comment&#x27;]&#x2F;&#x2F;text(), &#x27;user&#x27;: .&#x2F;&#x2F;a[@class=&#x27;hnuser&#x27;]&#x2F;@href, &#x27;parent_post&#x27;: .&#x2F;&#x2F;span[@class=&#x27;onstory&#x27;]&#x2F;a&#x2F;@href } </code></pre> Limitations: HTTP-only (no JS rendering yet), no crawl persistence. Both are on the roadmap if there&#x27;s interest.<p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;rodricios&#x2F;wxpath" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rodricios&#x2F;wxpath</a><p>PyPI: pip install wxpath<p>I&#x27;d love feedback on the expression syntax and any use cases this might unlock.<p>Thanks!

[DevOps] This Ansible collection provides battle tested hardening for Linux, SSH, nginx, MySQL

[CLI Tool] Show HN: Nori CLI, a better interface for Claude Code (no flicker) Hi HN, my name&#x27;s Clifford and I&#x27;m one of the creators of Nori. I’ve been using Claude Code heavily since last summer, and after understanding some of the tradeoffs with their TUI implementation, I knew I couldn&#x27;t see myself living for years with this interface as one of my daily-driver tools.<p>It is <i>not</i> a hard problem to make monospace text output performant, so why does Claude Code suffer from flicker and strobing in the terminal (<a href="https:&#x2F;&#x2F;github.com&#x2F;anthropics&#x2F;claude-code&#x2F;issues&#x2F;1913" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anthropics&#x2F;claude-code&#x2F;issues&#x2F;1913</a>)? Even after they&#x27;ve released multiple improvements for this, I still see the issue in terminal splits with fewer rows, or in less performant emulators, and even within a virtual TTY (the absolute simplest environment to run an interactive program in). After digging in throughout the past half year, the issue is mostly inevitable because Claude reprints full terminal history without using alt screen mode and uses a React-based framework (Ink) to render and style their text. That&#x27;s great for JS+CSS being &quot;on distribution&quot; for LLMs in order to vibecode the continued development of Claude Code, but it doesn&#x27;t deliver the experience I&#x27;d like. The frameworks they&#x27;ve chosen also have limitations around [terminal input parsing (i.e. the shift enter issues from last year: <a href="https:&#x2F;&#x2F;github.com&#x2F;anomalyco&#x2F;opencode&#x2F;issues&#x2F;1505#issuecomment-3411334883" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anomalyco&#x2F;opencode&#x2F;issues&#x2F;1505#issuecomme...</a>). Great terminal interfaces I&#x27;ve lived with for years (neovim, btop, helix, Cataclysm DDA, etc) don&#x27;t sacrifice user experience as a tradeoff for development convenience. They build resilient terminal interfaces on languages more appropriate for this problem, like C or C++ or Rust.<p>Finally, while I&#x27;m definitely rooting for Anthropic to continue improving their products, I can&#x27;t see myself coupling a commandline tool I use often with a single LLM provider. It would be insane if pushing my code to GitHub required me to edit it in VSCode — I want my tooling to do one thing well, and that&#x27;s display the read-eval-tool-loop from talking to an agent. Opus 4.5 has been stellar, but it&#x27;s nonnegotiable to me that I can try out varied providers with the same tools I plan to use everyday. Claude Code will not be working long term on how best to interface with multiple agents, from varying providers, in one terminal pane, and that makes perfect sense for their business. However based on our other experiences building out profiles and skillsets for agents, deeper customizations of agent instructions and subagents, and parallel worktrees for local agents, we have a lot of vision for how to handle local agentic work. And with the current design to integrate at the agent-level, we don&#x27;t plan on working around the OAuth flows or spoofing the system prompt outside of the Claude Code SDK (like with the OpenCode situation), and risk the tools coming into conflict with the providers.<p>These were the main considerations that went into designing Nori CLI. It&#x27;s a very thin and very fast TUI wrapper around multiple agent providers. It integrates with providers at the agent level, instead of the model level. Not only does that provide better performance in our experience, but that is also *compliant with current ToS for subscription based usage.* This is a very early version, but given the timing this week it might give you a flicker-free way to code with Claude Code!<p>The project is open source, and built on the stellar work by folks at Zed (on the abstraction over varied coding agents), and the folks working on Codex CLI (who have put together one of the nicest proprietary terminal experiences).<p>I&#x27;m very curious: What are the Claude Code features you couldn&#x27;t give up, to make the switch to a tool like this? What are the Claude Code features that work as intended, but you can&#x27;t stand?

[Other] Show HN: Webctl – Browser automation for agents based on CLI instead of MCP

[DevOps] Show HN: Run LLMs in Docker for any language without prebuilding containers I&#x27;ve been looking for a way to run LLMs safely without needing to approve every command. There are plenty of projects out there that run the agent in docker, but they don&#x27;t always contain the dependencies that I need.<p>Then it struck me. I already define project dependencies with mise. What if we could build a container on the fly for any project by reading the mise config?<p>I&#x27;ve been using agent-en-place for a couple of weeks now, and it&#x27;s working great! I&#x27;d love to hear what y&#x27;all think

[Other] A hub for vibe coding tools and developer resources. Vibe-Coding is a navigation site for vibe coding tools and development resources. We collect the best tools to boost your productivity. We've organized a comprehensive directory to cover every aspect of your developing workflow. Whether you're optimizing your process or personalizing your environment, you'll find what you need right here.

[Other] fastest way to backup dotfiles! Simple, fast, and built in TypeScript. Manage your dotfiles with Git, sync across machines, and never lose your configs again.

[Testing] Give LLMs access to web accessibility testing APIs A11y MCP is an MCP (Model Context Protocol) server that gives LLMs access to web accessibility testing APIs. This server uses the Deque Axe-core API and Puppeteer to allow LLMs to analyze web content for WCAG compliance and identify accessibility issues.

[Other] Inside The Internet Archive's Infrastructure <a href="https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3</a>

[Other] Claude Cowork runs Linux VM via Apple virtualization framework

[Other] Show HN: OpenWork – an open-source alternative to Claude Cowork hi hn,<p>i built openwork, an open-source, local-first system inspired by claude cowork.<p>it’s a native desktop app that runs on top of opencode (opencode.ai). it’s basically an alternative gui for opencode, which (at least until now) has been more focused on technical folks.<p>the original seed for openwork was simple: i have a home server, and i wanted my wife and i to be able to run privileged workflows. things like controlling home assistant, or deploying custom web apps (e.g. our customs recipe app recipes.benjaminshafii.com), legal torrents, without living in a terminal.<p>our initial setup was running the opencode web server directly and sharing credentials to it. that worked, but i found the web ui unreliable and very unfriendly for non-technical users.<p>the goal with openwork is to bring the kind of workflows i’m used to running in the cli into a gui, while keeping a very deep extensibility mindset. ideally this grows into something closer to an obsidian-style ecosystem, but for agentic work.<p>some core principles i had in mind:<p>- open by design: no black boxes, no hosted lock-in. everything runs locally or on your own servers. (models don’t run locally yet, but both opencode and openwork are built with that future in mind.) - hyper extensible: skills are installable modules via a skill&#x2F;package manager, using the native opencode plugin ecosystem. - non-technical by default: plans, progress, permissions, and artifacts are surfaced in the ui, not buried in logs.<p>you can already try it: - there’s an unsigned dmg - or you can clone the repo, install deps, and if you already have opencode running it should work right away<p>it’s very alpha, lots of rough edges. i’d love feedback on what feels the roughest or most confusing.<p>happy to answer questions.

[Other] Show HN: Cachekit – High performance caching policies library in Rust

[Other] Open sourcing Dicer: Databricks's auto-sharder

[IDE/Editor] Show HN: Nogic – VS Code extension that visualizes your codebase as a graph I built Nogic, a VSCode extension currently, because AI tools make code grow faster than developers can build a mental model by jumping between files. Exploring structure visually has been helping me onboard to unfamiliar codebases faster.<p>It’s early and rough, but usable. Would love feedback on whether this is useful and what relationships are most valuable to visualize.

[Other] Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN,<p>I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).<p>There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.<p>Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg&#x2F;s sustained (wrk2 @ 50K req&#x2F;s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.<p>Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion&#x2F;streaming workload).